Configuring an electronic device based on a transaction

ABSTRACT

A first network signal is received indicating a device identifier in response to a transaction involving an electronic device uniquely associated with the device identifier. An entity identifier specific to an entity associated with the transaction is determined. In response to an initialization event of the electronic device, a second network signal from the electronic device is received that identifies the electronic device. In response to the second network signal, a configuration is communicated to the electronic device that is specific to the entity associated with the transaction.

BACKGROUND

The present disclosure relates in general to consumer electronic (CE)devices, e.g., customization of devices based on supply chaintransactions. A common issue in the CE industry is that an intermediaryin the supply chain, such as a retailer, would like to have CE devicescustomized by the manufacturer for their specific needs. Thecustomization may be relatively minor, such as changing the color of thedevice, the texture of the finish, the user interface, the feature set,etc., to make the device unique for that retailer. This customizationenables the retailer to make claims that their devices that are unique,enhancing the perceived value of the device as compared to devices soldat other retail outlets.

However, customization of products at the factory can cause difficultiesfor the manufacturer. For example, customization may require changes inthe manufacturing process for each retailer. The manufacturer may haveto inventory several different stock-keeping-units (SKUs) of a certainproduct, one for each customized version. These burdens may cause themanufacturer to impose minimum unit requirements and/or customizationfees for such services. These fees are often too expensive for theretailer to pay, particularly in view of fierce price competition in theCE retail market.

SUMMARY

The present disclosure is generally directed to customization of devicesbased on supply chain transactions. In one embodiment, a method involvesreceiving a first network signal indicating a device identifier inresponse to a transaction involving an electronic device uniquelyassociated with the device identifier. An entity identifier specific toan entity associated with the transaction is determined, and in responseto an initialization event of the electronic device, a second networksignal is received from the electronic device that identifies theelectronic device. In response to the second network signal, aconfiguration is communicated to the electronic device that is specificto the entity associated with the transaction.

In another embodiment, a method involves determining, in response to atransaction involving an electronic device, a device identifier uniquelyassociated with the electronic device. At least the device identifier iscommunicated to a provisioning service in response to the transaction.The provisioning service determines an entity identifier of an entityassociated with the transaction and configures the electronic devicespecific to the entity in response to a signal sent to the configurationservice from the electronic device.

In another embodiment, an apparatus includes a data storage mediumconfigured during manufacture to store at least a device identifier thatdistinguishes the apparatus from other apparatuses of the same type. Aprocessor is configured to cause the apparatus to determine aninitialization event, and in response to the initialization event, senda network signal to a provisioning service. The network signalcommunicates at least the identifier. The processor is furtherconfigured to cause the apparatus to receive a device configuration inresponse to the network signal and apply the configuration to theapparatus. The device configuration is specific to an entity in a supplychain through which the device traveled. The device identifier is linkedto the entity via the provisioning service in response to a transactionoccurring in the supply chain.

The above summary not intended to describe each disclosed embodiment orevery implementation detail thereof. For a better understanding ofvariations and advantages, reference should be made to the drawingswhich form a further part hereof, and to accompanying descriptivematter, which illustrate and describe representative embodiments.

BRIEF DESCRIPTION OF THE DRAWINGS

In the following diagrams, the same reference numbers may be used toidentify similar/same components in multiple figures.

FIG. 1 is a block diagram illustrating a method and system according toan example embodiment;

FIG. 2 is a block diagram of a consumer electronic device according toan example embodiment;

FIG. 3 is a block diagram illustrating a procedure for initiallyestablishing service parameters for a device according to an exampleembodiment;

FIG. 4 is a block diagram illustrating a procedure for linking a devicewith an entity via a transaction according to an example embodiment;

FIG. 5 is a block diagram illustrating a procedure for applying changesto a device upon initialization/connection according to an exampleembodiment;

FIG. 6 is a block diagram of a server apparatus and system according toan example embodiment;

FIG. 7 is a flowchart illustrating a provisioning service procedureaccording to an example embodiment; and

FIG. 8 is a flowchart illustrating a service procedure according toanother example embodiment

DETAILED DESCRIPTION

In the following description of various example embodiments, referenceis made to the accompanying drawings that form a part hereof, and inwhich is shown by way of illustration various example embodiments. It isto be understood that other embodiments may be utilized, as structuraland operational changes may be made without departing from the scope ofthe present invention.

The present disclosure is related to systems and methods that facilitatecustomizing consumer electronic (CE) devices based on the desires of anintermediary, such as a retailer or distributor. For example, anInternet enabled electronic device can be enhanced or customizedpost-production based on certain criteria learned and obtained duringthe distribution or retail process. This enhancement may includeenabling new services or features, and/or providing a customizedexperience, e.g., a branded user interface.

Over the last few decades, CE devices have become not only morepervasive, but increasingly sophisticated. For example, evenspecial-purpose devices such as televisions and appliances may haveembedded processors with as much processing power as personal computersfrom decades past. These CE devices may also have other interfaces (suchas user and network interfaces) that allow the devices to performfunctions commonly associated with personal computers.

While the capabilities of modern CE devices may parallel those ofpersonal computers, consumer expectations of how such devices shouldoperate is markedly different from that of personal computers. Forexample, while users may be tolerant of the complexity that provides theability (or need) to highly customize a personal computer, more oftenthan not, they expect a traditional CE device to work right out of thebox without any further work beyond the initial setup. Nonetheless,there exists a desire among some to be able to customize a CE device.

For example, most CE devices are produced by original equipmentmanufacturers (OEMs) that often rely on economies of scale to makedevices that are affordable yet powerful and feature-rich. These devicesare sold in large quantities to wholesalers or large retailers, andeventually are made available to the end user via a seller, such as abricks-and-mortar store or Internet retailer. The competition betweenretailers is fierce, and the popularity of Internet sellers withextremely low margins means that even a large national retailer cannotalways depend on price alone to ensure sales volume.

One way in which retailers can distinguish themselves is to provideexclusive devices. For example, in the past, some retailers had OEMsproduce a store brand that the retailer alone was authorized to sell.These may have been custom designed products, although often were thesame as an existing OEM model but with different branding (e.g., logos,labels, colors, packaging). However, such custom branding can incursignificant costs, and may require large quantity orders to keep costsdown. Even then, savvy consumers may still be able to detect a rebrandedOEM product. Another disadvantage to store branding is that OEMs nowspend significant effort in advertising and building goodwill for totheir own brands, and it may be redundant (and even counterproductive)for a retailer to repeat that effort for a store brand that isfunctionally similar to a device branded by the OEM.

Instead of branding the external features of CE device, the presentdisclosure describes ways that entities in the supply chain cancustomize the internal state and/or function of a CE device when it isfirst activated (e.g., powered up) by the end user. This provides theappearance of a customized device, even though right out of the box, thedevice is substantially the same as other devices of the same typeproduced by an OEM. The embodiments described below allow CE deviceshaving, e.g., the same model/SKU, to exhibit a different end-userexperience due to a different channel of commerce through which thedevice traveled. The devices may be customized on initial setup and/orin response to any other event, such as initialization of newperipheral, software, service, etc., a software/firmware update,secondary sale or transfer of device, etc.

An example of a system and method that facilitates this devicecustomization according to an example embodiment is shown in the blockdiagram of FIG. 1. Generally, a manufacturer 102 is able to producedevices 104 that are substantially equivalent, e.g., all having the sameOEM model number, version number, etc. The OEM may assign a uniqueidentifier to each of the devices 104, such as a serial number. Theidentifier may be stored in a data storage medium of the device (e.g.,flash memory, radio frequency ID chip, write-once hardware registers,etc.).

Another source of device identifiers can be found in networkinghardware. Where devices 104 have built-in network interfaces, such asEthernet adapter or 802.11-type wireless adapter, the network interfacewill have a media access control (MAC) address that may be used as anidentifier. The MAC address may be universally administered, meaning itis uniquely assigned to a device by its manufacturer, the manufacturerbeing identified by the first three octets of the MAC address.Therefore, the manufacturer (or a supplier for the manufacturer) may beable to ensure that devices 104 have a unique MAC address fixed inhardware, in which case the MAC address can be used in a similar way asa serial number in identifying a device.

During transactions associated with the devices 104, information aboutthe devices 104 (e.g., represented by signals/paths 106-111) can belearned and associated with the devices 104 via a centralized entity112, e.g., third-party provisioning service provider. The centralizedentity 112 may include more than one apparatus or controlling party,e.g., a distributed entity acting as a single point of control. Thisassociation can be established by communicating at least the uniqueidentifier of the devices 104 along with the learned information 106,111. The learned information can be related to entities along the supplychain, which may include but are not limited to a distributor 114 whodistributes the devices 104, the retailers 116, 118 who receiverespective subsets of devices 104A, 104B for resale, and the buyers whobuy respective individual devices 104C, 104D. The buyers may be the sameas or different from end users 120, 122 who ultimately activate devices104C, 104D.

The transactions that trigger recording of information 106-111 mayinclude any significant event, pre- or post-sale, in which aconfiguration and/or reconfiguration may be desired. These transactionsmay include: the device being sold new or remanufactured; servicechanges related to the OEM 102, retailer 116, 118 and/or serviceprovider 112; changes in the OEM or retailer contact information (e.g.,phone number); attachment of a peripheral or other device with which theconfigured device may interact; device information that requiresupdating; etc.

The information 106-111 associated with the transaction may includeidentification of the selling retail channel (brick and mortar store,online, catalog, etc.), date, date range, extended servicessold/associated with the device, content service packages, extendedwarranties, promotional offers, accessories, etc. The learnedinformation 106-111 may vary based on aspects that are not necessarilydirectly related to the supply chain entities, such as time oftransaction (e.g., during trial period, during warranty, after warrantyexpires), geographic location in which transactions take place, localregulations, or any other criteria that may be learned and associatedwith the devices 104.

After the devices 104C, 104D are in the hands of the end users 120, 122,the devices 104C, 104D can establish connections with a provisioningservice (e.g., the centralized entity 112) in response to aninitialization event. The provisioning service 112 can access thelearned information, and in response provide information 110, 111 to thedevices to configure, enhance, update, and/or otherwise modify thedevices based on the desires of the channels through which the devicecame to the end-users 120, 122. The modifications may include modifyingthe user interface or any graphics or text placed on screens, skins(e.g., a graphical theme applied to user interface components),reposition of content service, phone numbers, logos, name of serviceofferings, ability to add new features or applications, addition/removalof content services (trial or permanent), addition/removal of featuresof the device, enabling/disabling features of the device (e.g.,affecting license fees), enabling/adding promotions,language/internationalization, etc.

It is to be understood that the end users 120, 122 may also participateas intermediaries in the supply chain. For example, consider a companythat installs electronic signage in buildings using commerciallyavailable televisions for displays. The company may purchase largequantities of televisions from a distributor and, depending on businessarrangements with customers regarding the devices (e.g., sell, lease),the company may be considered a reseller or an end user. The company mayneed each television to be set up in a particular way, and it could betime consuming to do so manually. In order to facilitate automaticconfiguration, the company could establish an account with thecentralized entity 112 and register each television set purchased, e.g.,using an optical scanner at a receiving dock. Thereafter, once thetelevisions are physically installed on-site, they may be automaticallyconfigured as desired after being powered on and connecting to anetwork. In such a case, the company may register a wide variety oftelevision models that they use for different types of installations.This could provide additional efficiencies, e.g., avoid having to traininstallers on how to configure different models of televisions.

As described above, the initialization event that triggers information110, 111 being sent to configure devices 104C, 104D may at least includea first power-on event and/or connection to a local network. Thisinitialization event may include any events that are detected by thedevices 104C, 104D, or detected elsewhere and communicated to thedevices 104C, 140D, either via the provisioning service 112 or by anout-of-band communications mechanism. For example, the event may betriggered by a change in information (e.g., an OEM's or retailer's phonenumber, device information), a change in a configuration of the device,the device becoming Internet enabled, device changing the type ofconnection, device being connected via a different service provider, newcontent services being offered, installed or enabled in the device, newdevices/peripherals are attached to the device (e.g. a new WiFi module,a new gaming device, etc).

The system and method shown in FIG. 1 allows manufacturers 102 toproduce a single SKU in a common way for multiple retailers 116, 118while still providing a way for the retailers 116, 118 to customize theproduct post-manufacturing, post-distribution, and/or after the producthas been sold through the retail channel. The retailers 116, 118 canidentify which devices have been sold through their channel and sharethe information with a provisioning service 112 which in turn managesthe customization of the device. The provisioning service 112 could beprovided, in whole or in part, by the manufacturer, the retailer or anyother third party service provider.

In reference now to FIG. 2, a block diagram illustrates functionalcomponents of a CE device 200 according to an example embodiment. Thisdiagram is intended to illustrate general functional components andinteractions for purposes of the discussion hereinbelow, and is notintended to limit the embodiment to the listed functions/features. Thedevice 200 includes hardware components 202 such as a processor 204,memory 206, and input/output (I/O) circuitry 208, that may performspecial-purpose or general-purpose computational tasks. The memory 206may include both volatile and non-volatile memory, the latter usable tostore programs and data (e.g., unique identifier of device 200 that canbe recorded on the memory 206 during manufacture).

The hardware 202 may also include specialized components for providing aprimary function of the device, as indicated by block 210. Thiscomponent 210 may be considered part of or separate from the I/Ocircuitry 208, and may perform functions such as display, sound,sensors, tuners, signal processors, conditioning circuitry, powersupplies, motors, etc. These functions may be those commonly associatedwith the device 200. For example, if the device 200 is a television, thefunctions may include hardware for display, sound reproduction, tuning,signal processing, switches for accepting user input, etc.

Various aspects of the functional components 210 (as well as othercomponents of the hardware 202) may be amendable to being customizedaccording to the desires of an intermediary in the supply chain. Thesecustomization options are represented here by customizable elements 212.The elements 212 may include any combination of hardware, executableinstructions, firmware, configuration data, content, etc., that can beselectably activated, deactivated, and/or modified to provide anexperience for the particular device 200 that distinguishes it fromother devices of the same type, e.g., having the same model number.

For example, element 214 relates to customization of a user interface.The user interface element 214 can provide many aspects of custombranding, e.g., emphasizing that the device 200 is special based on thechannel of commerce by which it arrived compared to the same model thatmight be obtained elsewhere. For example, where the device 200 hasdisplay hardware, the user interface component 214 may be used to affectsuch features as colors, graphics/logos, fonts, languages, menustructures, etc. The user interface component 214 may also be used toaffect other user interface features, such as sounds, buttons/switches,force-feedback devices, indicator lights, etc.

The user interface component 214 may also be used to modify, activateand/or deactivate certain functions/features at least by prevent a userfrom accessing them from the provided user interface. Others of theelements 212 may also provide a similar function independently of theuser interface. For example, element 216 may be able toactivate/deactivate certain hardware functions, e.g., by writing to aregister. The actions associated with the element 216 may also extend toactivating/deactivating software features such as protocols, codecs,drivers, etc., that may be dedicated to or separate from the hardwarefunctions. For example, if the device 200 has a microphone, the element216 may be able to selectively enable/disable the microphone, as well asenabling/disabling voice recognition software that uses the microphone,e.g., to process voice commands.

Element 218 represents configurable content and/or service providersthat may be associated with the device. For example, a device 200 suchas a television may have certain content stored such as pictures,videos, music, etc. This content may be for purely demonstrationpurposes, and/or may have another purpose (e.g., video instructionmanual). Similarly, service providers may provide similar content over anetwork, and may provide other data services known in the art. Exampleprovider services include streaming media, news, weather, cloud datastorage, channel listings, etc. The activation of these services and/orcontent could be contingent on a purchase that happenedcontemporaneously with the purchase of the device 200.

Element 220 represents default settings of the device 200 that may becustomized. These settings may be available in any device of this type,but element 220 could set some settings different than themanufacturer's for purposes of convenience, e.g., starting with adefault language/locale corresponding to a geographical location wherethe device 200 was sold. This may also tie in to other services/devicesthat were purchased with the device 200 (or beforehand, e.g., from thesame retailer). For example, if the device 200 was a television that waspurchased together with (or after) a set top box, universal remote, andHDMI cable, the defaults for the television and set-top box could be setto utilize the HDMI inputs/outputs at startup, and the remote could beprogrammed to default to the correct codes that will enable to remote tooperate the television and set-top box.

Also pertaining to the purchase of the device 200, certain warranty andservice information could be enabled via element 222. This element 222could configure a status screen that shows date of purchase, location ofpurchase, show/store a copy of the receipt, indicate remaining warrantyperiod, etc. The element 222 could also be configured to show access toextended warranties, service contracts, etc., that were purchased withthe device. In another example, the element 222 could customize userinterfaces to display phone numbers, uniform resource locators (URLs),etc., for obtaining service in case of a malfunction.

Element 224 represents configurability of advertising/promotions thatmay be made available via the device 200. For example, the device 200may have a service enabled via element 218 that provides special offersby the retailer from which the device 200 was purchased. The component224 could be used to activate limited time (e.g., expires 30 days frompurchase) offers, and be regularly updated to provider continuing offersvia the service.

In order to provide customization according to any of the elements 212,the apparatus 200 may include one or more functional modules, asrepresented by customization module 230. Generally, the customizationmodule 230 receives signals, e.g., via a network, having informationthat instructs the module 230 to perform an operation on one or morecustomizable elements 212. These signals may received in response to aevent detected/triggered by the apparatus 200, such as initialization ofthe apparatus 200, although similar information may communicated anytime during the life of the apparatus 200. The information received inthe signals may indicate both the affected elements 212 and the desiredmodification to said elements 212. The information may take any form,although in one example they may take the form of a structured data filesuch as an extensible markup language (XML) formatted file. In othercases, the information may include computer executable code, e.g.,firmware updates, programs, object files, applets, scripts, etc.

One functional component contained within module 230 is represented bynetwork access component 232. The network access component 232 may dealwith any aspects related to reaching a centralized entity (e.g., entity112 in FIG. 1) via a network for purposes of retrieving information froma provisioning service for customizing the device. These network aspectsmay include, but are not limited to, network discovery, routing, addresslookup, transport, and/or application level protocols (e.g., HTTP,HTTPS, FTP, etc.). It should be noted that, while the device 200 mayinclude a network interface (e.g., WiFi adapter), there may be alternateconnection means that the device 200 could use to access the centralizedentity 112. For example, another device such as smart phone, portablenetwork adapter, home computer, etc., could act as a network proxy forthe device 200. This secondary device could communicate with the device200 through common data transfer interfaces such as USB, Bluetooth,infrared data association (IrDA), powerline networking, etc.

Once the network access module 232 has enabled communication with acentralized entity 112, a database access module 234 can interact withthe entity 112 for purposes of querying, retrieving, parsing, locallystoring, and locally applying customization. The database access module234 may utilize any form of retrieval, such as file transfer requests,invoking Web Services methods (e.g., simple object access protocol, orSOAP), invoking methods via HTTP PUT/GET methods, structured querylanguage (SQL) queries, etc. The database access module 234 willgenerally pass this information along to an execution module 236, whichapplies the retrieved information to the customizable elements 212.

The execution module 234 generally performs sequences of tasks relatedto applying and verifying changes to the customizable elements 212.These tasks may be customized for each device 200, although forefficiency it may be preferable to utilize an interface layer (e.g.,application program interface or API) that enables a common executionmodule 236 to work with a wide variety of products. Intermediary code,as represented by OEM adapter 238, can be prepared for each product tointerface with custom hardware 202 and/or customizable elements 212associated with the particular device 200.

While the illustrated adaptations to the device facilitate a wide rangeof modification, the OEM may want to ensure a defaultbehavior/appearance that provides at least the advertised features andan appearance desired by the manufacturer. Default module 240 mayinclude instructions and/or data that provides this default state. Thismodule 240 may also act as a “safe” mode of operation, e.g., that can bedefaulted to in the event of an error in modules 230 and/or elements212. Finally, authentication module 242 can provide security. Forexample, the module 242 may ensure operation/activation any of themodules 240 and/or elements 212 is authorized. In the event somefunctions may require a payment or subscription, and so service providermay wish to make sure such features are not activated by unauthorizedparties. The authentication/security module 242 may also be used toconfirm integrity of hardware and software of the device 200, e.g., todetect and thwart attempts at tampering with the device 200.

In another configuration, the authentication module 242 may alsofacilitate storing and accessing a unique identifier of the device(e.g., serial number). The unique identifier may be stored in persistentstorage 206 during manufacture (e.g., firmware or hardware encoded) andis later used for receiving configuration data from a provisioningservice. The module 242 may provide a way of ensuring an alternateidentifier cannot be used. For example, although a MAC address can beunique, it can sometimes be changed (e.g., via a driver) through what issometimes referred to as MAC address cloning. In such a case, the module242 (or equivalent function) can ensure that the correct identifier issent to a provisioning service even if the MAC address of the networkinterface has been altered for purposes of network communications.

In reference now to FIG. 3, a block diagram illustrates an exampleprocess according to an example embodiment. The process begins with oneor more retailers 300, 302 and manufacturer 304 agreeing to whatelements 306 of a device 308 can be customized. Retailers 300, 302 maychoose respective sets 310, 312 of customization options. For example,the retailers 300, 302 may want to have respective GUI serviceinterfaces Y_(A), Y_(B) in a user interface of device 308 that directsthe consumer to the retailer's phone number or website for service.Retailer 302 may prefer to have one content service X enabled oremphasized while disabling or deemphasizing another content serviceprovider using setting X_(A). Retailer 304 may prefer a functionalcomponent Z of the device 308 enabled/disabled per setting Z_(B).

Any number of customizable attributes 306 can be enabled into the device308 by the manufacturers prior to shipment. The retailers 300, 302 canchoose which of these attributes can be changed and what they can bechanged to through the use of the embodiments described herein. If theretailers 300, 302 make no choice as to a particular option, then theOEM can provide defaults (e.g., elements X, Y, Z in 306 may representOEM defaults). The retailers 300, 302 and/or manufacturer(s) 304 canregister these elements (and descriptions thereof) in a centralizedservice 314. For example, the manufacturer 304 may predefine thedescription of the customizable elements 306, as well as allowablevalues of those elements 306. For example, GUI service interface Y maybe configured by providing a data file in an acceptable format (e.g.,markup language, digital image, etc.). The service provider option X andfunctional component Z may be defined (e.g., in a markup languagedocument) using selectable parameters, e.g., “enabled,” “disabled,”“first listed,” etc. This agreement between the 300, 302 and/ormanufacturer(s) 304 can be used to establish and/or populate a database316.

During the retail sales process, a procedure is used by each retailer totrack which devices have been sold by the retailer. An example of thisprocedure is shown in the block diagram of FIG. 4. In response to aparticular transaction, e.g., a sale of device 400, a unique identifier402 of the device 400 is captured. In the illustrated example, theidentifier 402 is a bar code that can be captured at a point of saleterminal 403, e.g., using an optical scanner. The identifier 402 may becaptured in other ways, such as radio frequency identifier (RFID) tag,optical character recognition, manual entry, etc. The identifier 402 maybe used alone, or in combination with another identifier 404, and isgenerally intended to ensure data pertaining to the device 400 can bepositively identified via a network service.

In some situations, the identifier 402 may be considered globallyunique, e.g., it is unlikely two items will have the same identifierregardless of the type of item. This may be the case where theidentifier 402 is a physical MAC layer address, for example. Uniquenessof a MAC address may be enforceable by way of the address range assignedto the manufacturer, and further by how the manufacturer assigns theaddresses within that range. A serial number used as identifier 402 mayor may not be globally unique. For example, it may be difficult formanufacturers to ensure unique serial numbers, as there may be nocentral entity that governs serial numbers in a way similar to MACaddresses. However, so long as the identifier 402 is unique for at leastthe particular type/model of device 400, a second identifier 404 may beused in combination with unique identifier 402 to ensure the device canbe uniquely identified for purposes of customization described herein.The secondary identifier 404 may include any one or more of part number,model number, SKU, version number, etc. In the description that follows,the description of the unique identifier 402 is understood to optionallyinclude the secondary identifier 404.

The device identifier data 402 can be captured at the time of sale andsent via a network to service 314 described in FIG. 3 that has knowledgeof prior agreements between manufacturers and distribution entities(e.g., retailers) regarding types of devices, of which device 400 is amember. The service 314 may include an affiliation of separate services,and different activities can be sent to different entities (e.g.,services, providers) within that affiliation. Generally, the service 314will store the communicated identifier 402 into a database 316, whichmay itself be a distributed and/or affiliated group of services.

Another piece of information that may be expressly or inherentlycommunicated to the service 314 regarding the transaction is anidentifier 408 of the entity (e.g., retailer) to which the transactionpertains. This identifier 408 may be expressly communicated with theidentifier 402 during the event, or may be inferred, e.g., by thechannel of communication used to communicate the device identifier 402.As shown by way of example SQL INSERT statement 410, the transactionresults in a linkage being created between the device identifier 402 andthe entity identifier 408. This linkage 410 could also be madeinherently, e.g., the retailer could have a dedicated table to whichdevice identifiers 402 are added. Also, the linkage 410 need not beexpressly made between device identifier 402 and entity identifier 408.For example, data describing a feature set for the device 400 could beobtained using the identifiers 402, 408, and a table could list/linkthis feature set with the device identifier 402. Thus, while the entityidentifier 408 is used to retrieve the feature set, the express linkagein such a case is made between the feature set and the device identifier402, and not between the device identifier 402 and the entity identifier408.

In reference now to FIG. 5, a block diagram illustrates additionalnetwork interactions between device 400 and service 314 that occur afterthe transaction described in FIG. 4. After the transaction, a softwarecomponent in the device 400 (referred to here as the device agent 502)enables the device 400 to register or connect with a provisioningfunction of service 314 upon initial connection of the device 314 to theInternet, or based on establishment of any other two-way communication.The device agent 502 may include functions the same as or similar tomodule 230 shown in FIG. 2.

The device agent 502 can determine to what provisioning service 314 towhich the device 400 can connect. For example, the device agent 502 maybe pre-configured with a built-in provisioning service identifier 504(e.g., URL). In other configurations, the device agent 502 may usenetwork service discovery to determine some or all aspects of theservice's identity. Upon initialization/connection of the device 400,the device agent 502 registers 506 the device 400 with the provisioningservice 314. The registration 506 may involve sending a uniqueidentifier associated with the device 400 so that the previously enteredlinkage data (e.g., via statement 410 in FIG. 4) can be obtained. Thisunique identifier may include device identifier 402 shown in FIG. 4, ormay be a new identifier, e.g., a hashed and/or encrypted value based onidentifier 402 and/or other data that can be stored on the device 400 atthe time it is manufactured.

As represented by SQL query 508 to database 316, the provisioningservice 314 determines a feature set 510 associated with the device 400.This feature set 510 is determined by linkage in the database 406 of theretailer that sold the device 400. The feature set 510 is also based onthe set of rules established by the manufacturer and the retailer forthis device 400. Additional features may be included in set 510 that mayhave occurred after the manufacturer and retailer established the rules.For example, the features may include a general purpose channel/featurefor providing bargains, advertising, offers, etc. via device 400, butthe actual content of that channel/feature may not be established untilthe transaction in FIG. 4 takes place, and may be different fordifferent end devices sold from the same retailer based on the contextof the transaction (e.g., other purchases, time, location, method ofpayment, device status, device interfaces, connected device status,learned demographic information, etc.).

The provisioning service 314 applies 512 the changes to the device 400via the Internet or using any other two-way communications. This mayinvolve the device 400 verifying, parsing, and applying communicateddata (e.g., feature set 510) to internal storage. This data 510 may bedirectly used to modify the device 400, and/or may be used to activatedata already stored on the device 400. After application of the data501, the device 400 has is enhanced and customized to the retailer'sneeds. This customization occurs without the manufacturer having to doit in the factory, and without the manufacturer having to inventoryseveral different SKUs of the same product, each customized for adifferent retailer. The customized attributes can be fixed for alldevices in a device group and/or can be defined on a per device basisbased on services sold with the device or promotions which apply to thedevice at time of sale. The retailer can make changes to theseattributes post sale as well based on whatever criteria they wish.

In reference now to FIG. 6, a block diagram illustrates a servicearrangement 600 according to an example embodiment. The servicearrangement can be used to provide provisioning and customizationservices as previously described, e.g., regarding services 112 and 314.The service arrangement 600 may include one or more service apparatuses602. The service apparatus 602 may include computing hardware such as aprocessor 604, memory 605, input/output hardware 606, user interfacehardware 607, and network interface 608.

The memory 605 may include volatile memory (e.g., random access memory,or RAM) and non-volatile memory (e.g., hard disk drives, solid-statedrives, optical media, etc.). The memory 605 can store instructions,represented as operational software 610, which are operable by theprocessor 604 to perform functions described herein. It will beunderstood that operations performed by software 610 may be implementedin whole or in part in hardware and/or firmware, and description offunctions being performed by software is not intended to be limiting.

As illustrated, the apparatus is coupled to one or more networks 612 vianetwork interface(s) 608 for communication with manufacturers 614,supply chain intermediaries 616, and consumer electronic devices 618.The interactions described between the service arrangement 600 andentities/devices 614, 616, 618 may also occur via other data transferinterfaces, including local I/O ports 606 and user interface 607.Generally, the modules shown as part of software 610 facilitate thesecommunications independently of the actual communication paths used.

The software 610 includes one or more OEM/retailer interfaces 620 thatprovide a common layer usable by manufacturers 614 and intermediariesfor managing customization features such as previously describedregarding FIGS. 1, 3 and 4. This module 620 may be used forfunction-independent aspects of communications, such as data transportprotocols, authentication, etc. The interface module 620 can passcontrol to other modules for performing specific tasks. For example, aconfiguration module 622 may facilitate establishing, modifying, anddeleting customization attributes for particular devices for whichagreements have been newly established. This module 622 may establishand/or modify tables of a database 634 used to centrally manage thecustomization attributes. Either or both of the manufacturer 614 andintermediaries 616 may be able to manage data via this module 622.

A linkage/update module 624 may be used by manufacturer 614 and/orintermediaries 616 to maintain in-process data related to individualdevices and/or classes of devices that have been previously establishedvia configuration module 622. For example, module 624 may handle linkingof purchases and other transactions to particular devices 618, such asCE devices described in FIGS. 1-5. This module 624 may also be used topush updates to those devices 618 after initialization. A metrics module626 may be able to track statistics related to device linkages,activations, etc., that may be of interest to both manufacturers 614 andintermediaries 616.

A separate interface 628 may be used to interact with devices 618 duringinitialization and possibly thereafter. As with interface 620, thisinterface 628 may deal with common connection tasks such as establishingconnections, data transport, authentication, etc. A registration module632 may handle device-initiated signaling that indicates the devices 618are ready to receive and initial configuration. An update module 630 maybe used to apply updates 618 to devices thereafter, either upon requestof the devices 618 or pushed to the devices 618 from the servicearrangement 600.

Generally, the arrangement 600 facilitates centralized operationsassociated with customizing individual devices 618. Customizationattributes for each device or device group (e.g., content services,support services, and/or other content that may be installed or enabledon the device) can be stored in database 634 for later retrieval. At anypoint during or after a sales transaction, the database informationregarding the device 618 and the attributes associated with thecustomization of the device 618 is transmitted or otherwise madeavailable for use to the provisioning service 600 when processing thedevice registration request. One option is for a database of informationto be stored locally (e.g., with retailer or other intermediary thatprocessed the transaction) and then made available to the partyresponsible for customization of the device (e.g., via a network serviceprovided by the intermediary). Another option is for the data to betransmitted to the customization service provider during or after thesales transaction.

At any time after the sales transaction concludes and a device 618 issetup for use, the device 618 establishes a connection with theprovisioning service 600. This process is referred to as deviceregistration. As part of the registration, or in a process that followsregistration, the provisioning service 600 utilizes the retail database634 to determine what customization should be applied to the device 618based on the rules setup for the customization. The provisioning service600 initiates the activities necessary to enable/disable,activate/deactivate, install/uninstall, update or otherwise change thedevice 618 to support the desired customization needs.

For purposes of illustration, the operation of the devices is describedin terms of functional circuit/software modules that interact to provideparticular results. Those skilled in the art will appreciate that otherarrangements of functional modules are possible. Further, one skilled inthe art can readily implement such described functionality, either at amodular level or as a whole, using knowledge generally known in the art.The computing structures are only a representative example of devicesand services that enable customizing CE devices as described herein. Forexample, the functions of the service arrangement 600 can be distributedover a large number of processing and network elements, and can beintegrated with other services, such as Web services, gateways, mobilecommunications messaging, etc. For example, the functions of the servicearrangement may be distributed between any combination of themanufacturer 614, one or more intermediaries 616, and a third party.

In reference now to FIG. 7, a flowchart illustrates a procedureaccording to an example embodiment. A first network signal is received700 indicating a device identifier, e.g., in response to a transactioninvolving an electronic device uniquely associated with the deviceidentifier. The device identifier may include at least one of serialnumber and a media access control address. The first network signal mayinclude additional data related to the transaction that is used tomodify the configuration of the electronic device specific to thetransaction. The additional data may include data describing anadditional transaction related to the electronic device.

At 702, an entity identifier specific to an entity associated with thetransaction is determined. The entity may include a retailer and/or anyother intermediary in the supply chain. In response to these previousoperations 700, 702, the electronic device may optionally 704 be linkedto the entity in a database in response to the first network signal.

In response to an initialization event of the electronic device, asecond network signal is received 706 from the electronic device thatidentifies the electronic device. In response to the second networksignal, a configuration may optionally be retrieved 708 via a database.In whatever way the configuration may be obtained, the configuration iscommunicated 710 to the electronic device that is specific to the entityassociated with the transaction.

In reference now to FIG. 8, a flowchart illustrates a procedureaccording to another example embodiment. In response to a transactioninvolving an electronic device, a device identifier uniquely associatedwith the electronic device is determined 800. The device identifier mayinclude at least one of serial number and a media access controladdress. At least the device identifier is communicated 802 to aprovisioning service in response to the transaction. An entityidentifier of an entity (e.g., a retailer) associated with thetransaction may optionally be communicated 804 to the provisioningservice.

Additional data related to the transaction may also be optionallycommunicated 806 to the provisioning service. The additional data isused to modify a configuration of the electronic device specific to thetransaction. The additional data may include data describing anadditional transaction related to the electronic device. The additionaltransaction may include any of: a purchase of a service contract relatedto the electronic device; content usable by the electronic device; anetwork service usable by the electronic device; and a second deviceusable with the electronic device.

At least one of these communications 802, 804, 806, causes 808 theprovisioning service to determine the entity identifier and configurethe electronic device specific to the entity in response to a signalsent to the configuration service from the electronic device.

The foregoing description of the example embodiments has been presentedfor the purposes of illustration and description. It is not intended tobe exhaustive or to limit the inventive concepts to the precise formdisclosed. Many modifications and variations are possible in light ofthe above teaching. It is intended that the scope of the invention belimited not with this detailed description, but rather determined by theclaims appended hereto.

The invention claimed is:
 1. A first electronic device comprising: adata storage medium configured during manufacture to store at least afirst device identifier that distinguishes the first electronic devicefrom other devices of the same type, and additional informationindicating a second electronic device interoperable with the firstelectronic device; a hardware processor configured to cause the firstelectronic device to: determine an initialization event; in response tothe initialization event, send a network signal to a provisioningservice, wherein the network signal communicates at least the identifierand the additional information; receive a device configuration inresponse to the network signal, wherein the device configuration isspecific to an entity in a supply chain through which the firstelectronic device traveled, and wherein the first device identifier islinked to the entity via the provisioning service in response to atransaction occurring in the supply chain, the device configuration toprogram the first electronic device to interoperate with the secondelectronic device in response to the initialization event; and apply thedevice configuration to the first electronic device.
 2. The firstelectronic device of claim 1, wherein the initialization event includesat least one of a first power-on of the first electronic device and afirst connection to a network by the first electronic device.
 3. Thefirst electronic device of claim 1, wherein the device configurationcustomizes at least one of a user interface and an operational functionof the first electronic device as specified by the entity.
 4. The firstelectronic device of claim 3, wherein the device configurationcustomizes the user interface to display any combination of contactinformation and graphical information associated with the entity.
 5. Thefirst electronic device of claim 1, wherein the network signal includesat least one of a hashed or an encrypted value derived from the firstdevice identifier, the at least one of the hashed or the encrypted valuelinked to the entity via the provisioning service.
 6. The firstelectronic device of claim 1, wherein the first device identifierincludes a media control address.
 7. A method comprising: storing, on adata storage medium during manufacture of a first electronic device, atleast a device identifier that distinguishes the first electronic devicefrom other devices of the same type, and storing additional informationindicating a second electronic device interoperable with the firstelectronic device; determining, by executing an instruction with aprocessor in the first electronic device, an initialization event; inresponse to the initialization event, sending, by executing aninstruction with the processor, a network signal to a provisioningservice, wherein the network signal communicates at least the identifierand the additional information; receiving, at the first electronicdevice, a device configuration in response to the network signal,wherein the device configuration is specific to an entity in a supplychain through which the first electronic device traveled, and whereinthe device identifier is linked to the entity via the provisioningservice in response to a transaction occurring in the supply chain, thedevice configuration to program the first electronic device tointeroperate with the second electronic device in response to theinitialization event; and applying the device configuration to the firstelectronic device.
 8. The method of claim 7, wherein the initializationevent includes at least one of a first power-on of the first electronicdevice and a first connection to a network by the first electronicdevice.
 9. The method of claim 7, wherein the device configurationcustomizes at least one of a user interface and an operational functionof the first electronic device as specified by the entity.
 10. Themethod of claim 9, wherein the device configuration customizes the userinterface to display any combination of contact information andgraphical information associated with the entity.
 11. The method ofclaim 7, wherein the network signal includes at least one of a hashed oran encrypted value derived from the device identifier, the at least oneof the hashed or the encrypted value linked to the entity via theprovisioning service.
 12. The method of claim 7, wherein the deviceidentifier includes a media control address.
 13. A non-transitorycomputer-readable storage medium comprising instructions thereon thatwhen executed by a processor, causes the processor to: store, on a datastorage medium during manufacture of a first electronic device, at leasta device identifier that distinguishes the first electronic device fromother devices of the same type, store additional information indicatinga second electronic device interoperable with the first electronicdevice; determine an initialization event; in response to theinitialization event, send a network signal to a provisioning service,wherein the network signal communicates at least the identifier and theadditional information; receive, at the first electronic device, adevice configuration in response to the network signal, wherein thedevice configuration is specific to an entity in a supply chain throughwhich the first electronic device traveled, and wherein the deviceidentifier is linked to the entity via the provisioning service inresponse to a transaction occurring in the supply chain, the deviceconfiguration to program the first electronic device to interoperatewith the second electronic device in response to the initializationevent; and apply the device configuration to the first electronicdevice.
 14. The non-transitory computer-readable storage medium of claim13, wherein the initialization event includes at least one of a firstpower-on of the first electronic device and a first connection to anetwork by the first electronic device.
 15. The non-transitorycomputer-readable storage medium of claim 13, wherein the deviceconfiguration customizes at least one of a user interface and anoperational function of the first electronic device as specified by theentity.
 16. The non-transitory computer-readable storage medium of claim15, wherein the device configuration customizes the user interface todisplay any combination of contact information and graphical informationassociated with the entity.
 17. The non-transitory computer-readablestorage medium of claim 13, wherein the network signal includes at leastone of a hashed or an encrypted value derived from the deviceidentifier, the at least one of the hashed or the encrypted value linkedto the entity via the provisioning service.
 18. The non-transitorycomputer-readable storage medium of claim 13, wherein the deviceidentifier includes a media control address.
 19. The first electronicdevice of claim 1, wherein the second electronic device is a set topbox.